CloudSocket Roles
This page defines users and roles involved in CloudSocket. It heavily references the different types of process models used by the suite.
<<TableOfContents>>Business Process Designer
The Business Process Designer creates Business Process Models (Level-I processes) using the CloudSocket Design tool. The processes reference an Ontology provided by an Ontology provider. In practice, the Business Process Designer may be a Business Consultant or a CloudSocket Broker.
Executable Process Designer
The Executable Process Desiger creates an Executable Business Process (Level-II process) based on a Business Process Model; mapping tasks to a workflow of service invocations. In practice, the Executable Business Designer may be a 'Technical' Consultant, a service provider, or a CloudSocket broker.
Deployable Process Modeller
The Deployable Process Modeller builds a BPaaS Cloudlet based on an Executable Business Process (Level-III process); mapping references to service types to service instances offered by service providers. In practice, the Executable Business Designer may be a 'Technical' Consultant, a service provider, or a CloudSocket broker.
CloudSocket Broker
The main task of the broker besides the fact that it can be contributing to defining the various models is that it selects deployable (Level-III processes) and offeres them to its users (Business Process Users). Hence, it takes a Level-III process and renders it to something executable. Hence, a CloudSocket Broker is the responsible to publish the business process. Moreover, it is the responsible to manage the discovery, orchestration, deployment and execution of services on the cloud, allowing the customer to use and exploit them. The broker is someone who acts as an intermediary between two or more parties during the negotiation, acting as intermediary between the purchaser of the cloud computing service and the sellers of that business process as a service.
Business Process User
User of CloudSocket in the sense that it unlocks a Business Process for a dedicated group of end users (the tenant).\\
End User
The actual person/set of persons interacting with the Business Process realised through the Cloudlet, e.g. a case worker in a personnal department. Very likely that this person belongs to the same institution as the operator.
BPaaS Provider
Offers one or multiple business processes to Business Process Users. Runs these under its own control either using own hardware or further P/IaaS offerings.
External Service Provider
Organization installing, executing and managing a service instance that Level-III processes can be bound to. Also, the External Service Provider autonomously defines SLAs for the Service and is responsible to fulfill such SLA. He is paid according to the usage of the Service he provides.
Proposal to discuss
Classification
We use the classification as stated in [1]:
A (Business) actor is an organisational entity able to perform certain behavior.
A (Business) role is the responsibility of performing a certain behavior to which an actor can be assigned.
Actors
Roles
Process Designer
Designs business processes.
To discuss...
Kyriakos: We can have specialisations of the form: Business Process Designer and Executable Process Designer. The latter specialisation could also be named as Workflow Designer (as workflows are executable processes).
Consultant
Consults an organisation when designing a BPaaS. It can be discriminated into a Business and Technical Consultant. Some good definitions can be found on Section 6.7 of the D4.1 Deliverable.
CloudSocket Broker
To discuss...
Kyriakos: can be actually replaced by BPaaS provider as the broker, in the way we define it, actually offers pre-packaged BPaaSs to its clients
External Service Provider / Cloud Service Provider
To discuss...
Kyriakos: As Cloud Service Provider, this role can be specialized to the roles of BPaaS Provider, SaaS Provider, PaaS Provider and IaaS Provider
Business Process User
To discuss...
Kyriakos: Role, not a User. Should be renamed into BPaaS Client to indicate that we deal with an organisation which desires to purchase and exploit a particular BPaaS offered by a BPaaS Provider.
End-User
To discuss...
Kyriakos: Role, not a User. I propose to rename it to BPaaS Participant which can be further specialized into BPaaS Knowledge Worker.
CloudSocket Operator
It is the one offering the BPaaS platform through which a BPaaS Provider can offer its BPaaSs. It could also be specialized into 5-6 sub-roles mapping to the respective environments that need to operate and be integrated in order to comprise the BPaaS platform.
Software Developer
Develops sopftware which will lead to completing the required functionality of a BPaaS. In case there is a need for a software which is not available (via external SaaS or open-source software libraries).
System Architect / BPaaS Allocator
This is a role responsible for concretizing a BPaaS and setting up its suitable configuration as well as its adaptation capabilities.
This represents a better name with respect to Deployable Process Modeller. In addition, there is a problem in the second sentence in the definition of the Deployable Process Modeller.
Business Engineer
Responsible for defining strategic business requirements/goals and respective organisational business processes.
[1] http://pubs.opengroup.org/architecture/archimate2-doc/chap03.html [2] M. Weske. Business Process Management - Concepts, Languages, Architectures. Springer, 2007.
Funding Partners
Horizon 2020